1.1. Here is the original idea we decided to go with. We will be using the topics form the following chapters:
1.1.1. Chapter 19 Threading & Synchronization
1.1.2. Chapter 20 Security
1.1.3. Chapter 23 Windows Services
1.1.4. Chapter 24 Interoperability
1.1.5. Chapter 25 Manipulating Files and the Registry
1.2. Create a client-server architecture of a secure message service. The client program will have a simple interface. The user selects the person they want to communicate with. They type a message and select send. The program uses a thread (CH 19) to encrypt (CH 20) the message text and send it off to the server. This is accomplished my using the Windows interoperability function Marshaling (CH 24) to communicate between programs. The server opens a socket (CH 23) to send the message to the other server program at the destination. The server then creates a log (CH25) of the communication activity. The programs connect with each other using Registry (CH 25) information.
1.3. David and I had a meeting to finalize the concept and we each took a part of the program to do. David selected to work on the client aspect and I took the server part. We wanted to work out the major parts of these areas and would incorporate the other features when the main parts of our individual projects were completed.
1.4. As it turns out we each ended up creating a chat program. It was a difficult concept to implement in a client/server environment because of the nature of the communication. To put it in the architecture of this environment we would had to add a lot of complexity to the project that wasn’t necessary. But that wasn’t apparent at the beginning as you will see.
Original Idea
1. Original Idea
1.1. Here is the original idea we decided to go with. We will be using the topics form the following chapters:
1.1.1. Chapter 19 Threading & Synchronization
1.1.2. Chapter 20 Security
1.1.3. Chapter 23 Windows Services
1.1.4. Chapter 24 Interoperability
1.1.5. Chapter 25 Manipulating Files and the Registry
1.2. Create a client-server architecture of a secure message service. The client program will have a simple interface. The user selects the person they want to communicate with. They type a message and select send. The program uses a thread (CH 19) to encrypt (CH 20) the message text and send it off to the server. This is accomplished my using the Windows interoperability function Marshaling (CH 24) to communicate between programs. The server opens a socket (CH 23) to send the message to the other server program at the destination. The server then creates a log (CH25) of the communication activity. The programs connect with each other using Registry (CH 25) information.
1.3. David and I had a meeting to finalize the concept and we each took a part of the program to do. David selected to work on the client aspect and I took the server part. We wanted to work out the major parts of these areas and would incorporate the other features when the main parts of our individual projects were completed.
1.4. As it turns out we each ended up creating a chat program. It was a difficult concept to implement in a client/server environment because of the nature of the communication. To put it in the architecture of this environment we would had to add a lot of complexity to the project that wasn’t necessary. But that wasn’t apparent at the beginning as you will see.
Project Home Next Section